Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

Dynamic object naming conventions

Dynamic objects use the same naming conventions as tables. From the previous example, the default dynamic Progress SmartDataBrowser™ with all table fields displayed is named rycagfullb. Other browsers would have names ending in b. This convention automatically groups procedures and objects pertaining to a particular table in a sorted listing of filenames or object names. The standard final letter makes it easy to identify the type of object.

Note: This convention is the reverse of the standard ADM2 convention of beginning filenames with one or more letters that identifies the type. Either convention can work; using a consistent standard is the important goal.

Progress Dynamics keeps track of both static (physical) and dynamic (logical) objects in its Repository. For a dynamic object, the Repository stores all the data needed to define and generate the object at run time. The object’s name (such as rycagfullb) is simply a key for locating the object; it does not correspond to any physical source file. Even though procedural objects are run as Progress r-code, they are also registered in the Repository. The default Repository name for these objects is the filename of the procedural object with its extension, product module, and relative path.

The relative pathname and filename extension of a procedural object are stored in different fields from the object name. There is no significant difference between the names of static and dynamic objects. The product module name is included in the filename by default.